Electronic wallet device for business transactions

ABSTRACT

An example device may include a plurality of card slots configured to hold at least two transaction cards, each card slot, of the plurality of card slots, including a card reader, one or more memories; and one or more processors, communicatively coupled to the one or more memories, to receive transaction information associated with a transaction at a transaction terminal; identify business information associated with the transaction; select a transaction card from the at least two transaction cards based on the transaction information and the business information; and provide a transaction token, associated with the selected transaction card, to be used in connection with the transaction terminal to process the transaction.

BACKGROUND

Transaction cards (e.g., credit cards, debit cards, gift cards,automated teller machine (ATM) cards, rewards cards or client loyaltycards, and/or the like) and/or devices (e.g., a smart transaction card,a smartphone, and/or the like) may be used in transactions to pay forproducts or services at transaction terminals (e.g., point of sale (PoS)terminals) of individuals or businesses engaged in the sale of goods orservices. The transaction cards may include an integrated circuit (IC)chip to improve security with respect to use of the transaction card.Utilizing such “chip cards” requires physically inserting the cards intoa card reader. The integrated circuits may include a secure element,which is required in order to validate and/or authenticate a transactionutilizing the chip card. Newer card readers may use contactlesstechnologies, such as near field communication (NFC) or Bluetooth LowEnergy (BLE) technologies and/or the like, to allow communicationsbetween the transaction terminal and a transaction card, with attendantadvantages. Many existing chip cards are not compatible with suchcontactless payment terminals.

SUMMARY

According to some implementations, an electronic wallet device mayinclude a plurality of card slots configured to hold at least twotransaction cards, each card slot, of the plurality of card slots,including a card reader, one or more memories; and one or moreprocessors, communicatively coupled to the one or more memories, toreceive transaction information associated with a transaction at atransaction terminal; identify business information associated with thetransaction; select a transaction card from the at least two transactioncards based on the transaction information and the business information;and provide a transaction token, associated with the selectedtransaction card, to be used in connection with the transaction terminalto process the transaction.

According to some implementations, a non-transitory computer-readablemedium storing instructions, that, when executed by one or moreprocessors of an electronic wallet device, may cause the one or moreprocessors to receive transaction information associated with atransaction at a transaction terminal; identify business informationassociated with a time period of the transaction; identify a set ofcandidate transaction cards to be used for the transaction, the set ofcandidate transaction cards comprising respective integrated circuit(IC) chips that are communicatively coupled with a card reader of theelectronic wallet device; select a transaction card from the set ofcandidate transaction cards, the transaction card being selected basedon the business information; and provide a transaction token, associatedwith the transaction card, to the transaction terminal.

According to some implementations, a method may include detecting, by anelectronic wallet device, a transaction pending at a transactionterminal, the electronic wallet device holding at least two transactioncards; obtaining, by the electronic wall device, business informationassociated with a time period of the transaction; selecting, by theelectronic wallet device, a transaction card from the at least twotransaction cards, the transaction card being selected based on at leastone of: the business information, or transaction information associatedwith the transaction; obtaining, by the electronic wallet device, atransaction token associated with the transaction card; and providing,by the electronic wallet device, the transaction token to thetransaction terminal.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1C are diagrams of an overview of an example implementationdescribed herein;

FIG. 2 is a diagram of an example environment in which systems and/ormethods, described herein, may be implemented;

FIG. 3 is a diagram of example components of one or more devices of FIG.2;

FIG. 4 is a flow chart of an example process that may be implemented inassociation with an electronic wallet device described herein;

FIG. 5 is a flow chart of an example process that may be implemented inassociation with a smart transaction card and an electronic walletdevice described herein;

FIG. 6 is a flow chart of an example process that may be implemented inassociation with a user device and an electronic wallet device describedherein;

FIGS. 7A-7C are diagrams of an example implementation relating toexample processes shown in FIGS. 4, 5, and/or 6;

FIGS. 8A-8C are diagrams of an example implementation relating toexample processes shown in FIGS. 4, 5, and/or 6; and

FIGS. 9-12 are diagrams of example implementations of an electronicwallet device described herein.

DETAILED DESCRIPTION

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

Transaction cards may be used to facilitate processing transactions attransaction terminals (e.g., point of sale (PoS) terminals, automatedteller machine (ATM) terminals, access terminals (e.g., lockingmechanisms for gates, doors, rooms, and/or the like), reward redemptionterminals, and/or the like). In many instances, consumers may haveaccounts with multiple entities (e.g., financial institutions (e.g.,banks), merchants, card associations, and/or the like) and/or may haveaccounts for multiple purposes (e.g., business purposes, specific typesof business purposes, personal purposes, and/or the like). Accordingly,consumers may carry multiple transaction cards while utilizing thetransaction cards in transactions (e.g., purchasing goods or services,redeeming loyalty/rewards points, redeeming store credit/gift cards,and/or the like). In some instances, consumers may prefer to useparticular cards for particular goods or services of a transaction basedon business uses associated with the transaction cards (e.g., expensingtransactions, inventory purchases, and/or the like) and/or transactioninformation associated with the transaction (e.g., merchant identifierindicating a type of merchant involved in the transaction, a monetaryvalue of the transaction, location information corresponding to alocation of the transaction, a currency used in the transaction, and/orthe like).

Some implementations, disclosed herein, provide an electronic walletdevice to facilitate processing transactions at a transaction terminal(e.g., a point of sale (PoS) terminal). The electronic wallet device mayreceive transaction cards (e.g., by a user inserting the transactioncards into card slots of the electronic wallet device) that may be usedin the transactions. The electronic wallet device may allowcommunication of a transaction token from one or more of the transactioncards to the transaction terminal to facilitate the transaction, eitherdirectly or indirectly. In some implementations, the electronic walletdevice may select a transaction card from a plurality of transactioncards inserted into the electronic wallet device to communicate atransaction token to the transaction terminal for the transaction basedon transaction information associated with the transaction terminal,based on business information associated with the transaction ortransaction card, based on user input, and/or the like.

Accordingly, some implementations described herein enable consumers toutilize a single device (i.e., an electronic wallet device) tofacilitate transactions between transaction terminals and a plurality oftransaction cards (e.g., rather than the consumer individually selectingand physically using the transaction cards at the transactionterminals). For example, the electronic wallet device may provide orcommunicate transaction tokens associated with the transactions cards totransaction terminals without consumers removing the transaction cardsfrom the electronic wallet device. Furthermore, some implementationsherein may enable automatic selection of an appropriate transaction cardbased on transaction information associated with the transaction and/ortransaction terminal (e.g., merchant type, transaction type, monetaryvalue of transaction, location information corresponding to a locationof transaction, and/or the like) and/or business information associatedwith the transaction (e.g., calendar information associated with thetransaction, message information associated with the transaction,authorization information for the transaction, and/or the like).Further, some implementations herein may provide an enhanced experiencefor consumers when engaging in transactions by enabling consumers toavoid selecting a transaction card to be used that ultimately may causea consumer to use a personal card rather than a business card, perhapsresulting in an inability to expense a transaction. Additionally,consumers, using an electronic wallet device described herein, may avoidshuffling through multiple transaction cards and/or personal items tofind a business transaction card for a business transaction and/or apersonal transaction card for a personal transaction. According to someimplementations, transaction errors or failures may be avoided using anelectronic wallet device as the electronic wallet device may avoidselecting or using transaction cards, for a transaction, that may bedeclined (e.g., by determining that a particular transaction may resultin credit limits of accounts of the transaction cards to be reached orexceeded), thus saving network resources and/or transaction terminalresources.

FIGS. 1A-1C are diagrams of an overview of an example implementation 100described herein. In example implementation 100 of FIGS. 1A-1C anelectronic wallet device is used in a transaction with a transactionterminal. In FIGS. 1A-1C, the electronic wallet device holds transactioncards that may be used in the transaction without being removed from theelectronic wallet device.

As shown in FIG. 1A, and by reference number 110, the transaction cards1-3 are inserted into the electronic wallet device. For example, aconsumer may insert the transaction cards into card slots of theelectronic device by sliding the transaction cards into the card slotsuntil integrated circuit (IC) chips (e.g., a EUROPAY®, MASTERCARD®,VISA® (EMV) chip) of the transaction cards are in electrical contactwith contacts of the electronic wallet device. As shown by referencenumber 120, information associated with the transaction cards may beobtained by the electronic wallet device. For example, a hub of theelectronic wallet device may obtain card information and/or businessinformation associated with the transaction card. More specifically, thehub may obtain balance information associated with an account of thetransaction card, credit limit information associated with an account ofthe transaction card, information indicating that the transaction cardis to be used for business transactions, information indicating that thetransaction card is not to be used for business transactions,information associated with one or more spend thresholds (e.g., perdiems) of the transaction card, and/or the like. In someimplementations, the electronic wallet device of example implementation100 may obtain the information from a user input, from a device incommunication with the electronic wallet device (e.g., a computer, asmartphone, and/or the like), via a network accessible to the device,and/or the like. In some implementations, the electronic wallet devicemay store the information associated with the transaction cards in thehub (e.g., in a data store of the hub).

As shown in FIG. 1B, and by reference number 130, a smart transactioncard associated with the electronic wallet device may be used tofacilitate processing a transaction at a travel merchant transactionterminal. For example, the smart transaction card may be associated withthe electronic wallet device by being communicatively coupled with theelectronic wallet device (e.g., via a wired or wireless communicationlink, such as a Bluetooth communication link, a Bluetooth low energy(BLE) communication link, a Wi-Fi communication link, and/or the like).The smart transaction card may engage in the transaction via anintegrated circuit (IC) chip of the smart transaction card (e.g., bybeing inserted into a card reader of the transaction terminal), via amagnetic strip of the smart transaction card (e.g., by being swiped),via a radio frequency (RF) antenna (e.g., via a near field communication(NFC) with the transaction terminal), and/or the like. As shown byreference number 140, the smart transaction card notifies the electronicwallet device of the pending transaction (e.g., via a transactionnotification message) and provides a merchant identifier associated withthe transaction terminal. For example, the smart transaction card mayprovide a merchant identifier indicating that the transaction is with atransaction merchant.

As shown in FIG. 1C, and by reference number 150, the electronic walletdevice obtains business information from a user device. The user devicemay be communicatively coupled (e.g., via a wired or wirelesscommunication link, such as a Bluetooth communication link, a Bluetoothlow energy (BLE) communication link, a Wi-Fi communication link, and/orthe like) with the user device to obtain the business information. Suchbusiness information may include calendar information (e.g., from acalendar application the user device), message information (e.g., from amessaging application of the user device), authorization information(e.g., from an application associated with the electronic walletindicating allowable business transactions (e.g., based on merchantidentifier, based on timing, based on geographical location, and/or thelike)), location information, and/or the like.

As shown by reference number 160, the electronic wallet device mayselect a business transaction card or non-business transaction card(e.g., a personal transaction card) for the transaction from transactioncards 1-3. For example, because the merchant identifier of thetransaction indicates that the transaction is with a travel merchant(which may commonly be an expensable business transaction), theelectronic wallet device may determine whether the business informationfrom the user device indicates travel plans associated with a business.For example, a business calendar of a consumer of the electronic walletdevice and/or user device may indicate that that the user is to betraveling at the time of the transaction. As such, the electronic walletdevice may select a business transaction card from transaction cards 1-3(e.g., one of transaction cards 1-3 that may be designated as a businesstransaction card). On the other hand, if the business information fromuser device does not indicate business related travel at or near thetime of the transaction, the electronic wallet may select a non-businesstransaction card from the transaction cards 1-3 in the electronic walletdevice.

As further shown in FIG. 1C, and by reference number 170, the electronicwallet device communicates the transaction token of the selectedtransaction card to the smart transaction card. For example, theelectronic wallet device may communicate the transaction token via acommunication link with the smart transaction card. As shown byreference number 180, the smart transaction card provides thetransaction token to the transaction terminal to facilitate processingthe transaction using funds from an account associated with the selectedtransaction card.

As illustrated in example implementation 100 of FIGS. 1A-1C, User A,when purchasing travel arrangements at a transaction terminal, mayutilize an electronic wallet to provide a transaction token from atransaction card of the electronic wallet. Furthermore, the electronicwallet device may effectively select an appropriate transaction card forthe transaction based on business information associated with User Aand/or the transaction as indicated by the merchant identifier.Accordingly, User A may have an enjoyable transaction experience withoutneeding to determine which transaction card is to be used for aparticular transaction or having to shuffle through User A's multipletransaction cards or personal items to find an appropriate businesstransaction card or non-business transaction card.

As indicated above, FIGS. 1A-1C are provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIGS. 1A-1C.

FIG. 2 is a diagram of an example environment in which systems and/ormethods, described herein, may be implemented. As shown in FIG. 2,environment 200 may include an electronic wallet device 210, a smarttransaction card 220, a transaction terminal 230, a user device 240, anetwork 250, a transaction backend 260, and a cloud computingenvironment 270 that hosts a business platform 280. In environment 200,electronic wallet device 210, smart transaction card 220, transactionterminal 230, and/or user device 240 may communicate data, between oneanother, that is associated with or related to a transaction withtransaction terminal 230, which facilitates processing the transactionthrough communication with transaction backend 260 via network 250.Devices of environment 200 may interconnect via wired connections,wireless connections, or a combination of wired and wirelessconnections.

Electronic wallet device 210 includes a device that may receive or docktransaction cards (e.g., credit cards, debit cards, access cards, clientloyalty cards, gift cards, and/or the like). Electronic wallet device210 may include one or more card slots configured to hold thetransaction cards. Each card slot, of the one or more card slots, mayinclude a card reader (e.g., a chip reader). Electronic wallet device210 may include a switching component that enables electronic walletdevice 210 to obtain transaction tokens and/or information (e.g., cardidentification information) from transaction cards in electronic walletdevice 210 and/or provide the transaction tokens and/or information tocomponents of environment 200. An example switching component mayinclude a conductive link (e.g., a trace, a wired connection, and/or thelike) and/or one or more switches. In some implementations, electronicwallet device 210 may include a hub with a processor and/or acommunication interface (e.g., a Bluetooth interface, BLE interface, aWi-Fi interface, a NFC interface, a cellular communication interface,and/or the like). For example, the hub may facilitate communicationbetween electronic wallet device 210 and the components of environment200. In some implementations, electronic wallet device 210 may bemodular in that components of electronic wallet device 210 (e.g., cardslots, a hub, a switching component, and/or the like) may be addedand/or removed from electronic wallet device 210 to enable electronicwallet device 210 to be adjustable and/or to hold more or lesstransaction cards, to increase or decrease the functionality ofelectronic wallet device 210, and/or the like.

Smart transaction card 220 includes a transaction card capable ofcommunicating with the components of environment 200 (e.g., viaBluetooth communication, BLE communication, Wi-Fi communication, NFCsession, and/or the like). Smart transaction card 220 is capable ofcommunicating data for a transaction with transaction terminal 230. Forexample, smart transaction card 220 may communicate data including atransaction token, transaction card identification information (e.g., anaccount identifier, a cardholder identifier, and/or the like), accountinformation, banking information, transaction information (e.g., atransaction token), and/or the like associated with transaction cardsheld in electronic wallet device 210. For example, to communicate thedata, smart transaction card 220 may include a magnetic strip and/or anintegrated circuit (IC) chip (e.g., a EUROPAY®, MASTERCARD®, VISA® (EMV)chip). Smart transaction card 220 may include an antenna to communicatedata associated with smart transaction card 220. The antenna may be apassive RF antenna, an active RF antenna, and/or a battery-assisted RFantenna.

In some implementations, smart transaction card 220 may communicate dataassociated with transaction terminal 230 to electronic wallet device 210and/or user device 240. For example, after an interaction withtransaction terminal 230 that may engage in a transaction (e.g., aftersmart transaction card 220 is swiped through a magnetic strip reader,after smart transaction card 220 is inserted into a card reader oftransaction terminal 230, after smart transaction card 220 has an NFCsession with transaction terminal 230, and/or the like), smarttransaction card 220 may obtain transaction information from transactionterminal 230. For example, transaction terminal 230 may obtain and/orprovide transaction information including information associated with anentity that owns or operates the transaction terminal, such as amerchant identifier, acceptable forms of payment, acceptable types oftransaction cards, a monetary value associated with the transaction(e.g., an amount or value of funds to be exchanged in the transaction),a location information corresponding to a location of the transaction(e.g., a geographical region, country, and/or the like), and/or thelike. Such transaction information may be used by electronic walletdevice 210 to select a transaction card (and/or an account associatedwith a transaction card) held in electronic wallet device 210 that is tobe used in the transaction (e.g., by providing a transaction token totransaction terminal 230).

Transaction terminal 230 includes one or more devices capable ofreceiving, generating, storing, processing, and/or providing informationassociated with facilitating a transaction (a PoS transaction). Forexample, transaction terminal 230 may include a communication deviceand/or computing device capable of receiving data from smart transactioncard 220 and/or a transaction card of electronic wallet device 210 andprocessing a transaction based on the data. In some implementations,transaction terminal 230 may include a desktop computer, a laptopcomputer, a tablet computer, a handheld computer, and/or a mobile phone(e.g., a smart phone, a radiotelephone, and/or the like). Transactionterminal 230 may be owned and/or operated by one or more individuals orbusinesses engaged in a sale of goods or services (e.g., one or moremerchants, vendors, service providers, and/or the like). In someimplementations, after an interaction with smart transaction card 220and/or a transaction card, transaction terminal 230 may provide orindicate transaction information associated with a transaction to smarttransaction card 220 and/or the transaction card. For example,transaction terminal 230 may indicate a merchant identifier, acceptableforms of payment for the transaction, acceptable types of transactioncards that may be used in the transaction, a monetary value associatedwith the transaction, a currency used in the transaction, locationinformation corresponding to a location of the transaction, and/or thelike.

Transaction terminal 230 includes one or more devices to facilitateprocessing a transaction via a transaction card and/or smart transactioncard 220. Transaction terminal 230 may include a PoS terminal, asecurity access terminal, an ATM terminal, and/or the like. Transactionterminal 230 may include one or more input devices and/or output devicesto facilitate obtaining transaction card data from smart transactioncard 220 and/or from an interaction or authorization from a cardholderof smart transaction card 220. Example input devices of transactionterminal 230 may include a number keypad, a touchscreen, a magneticstrip reader, a chip reader, and/or an RF signal reader. A magneticstrip reader of transaction terminal 230 may receive transaction carddata as a magnetic strip of smart transaction card 220 is swiped alongthe magnetic strip reader. A chip reader of transaction terminal 230 mayreceive transaction card data from an IC chip (e.g., an EMV chip) ofsmart transaction card 220 when the chip is communicatively coupled withthe chip reader. An RF signal reader of transaction terminal 230 mayenable contactless transactions from smart transaction card 220 byobtaining transaction card data wirelessly from smart transaction card220 as smart transaction card 220 comes within a range of transactionterminal 230 that the RF signal reader may detect an RF signal from anRF antenna of smart transaction card 220. Example output devices oftransaction terminal 230 may include a display device, a speaker, aprinter, and/or the like.

User device 240 includes one or more devices capable of receiving,generating, storing, processing, and/or providing information associatedwith facilitating a transaction using transaction cards of electronicwallet device 210 in accordance with some implementations herein. Forexample, user device 240 may include a communication and/or computingdevice, such as a mobile phone (e.g., a smart phone, a radiotelephone,and/or the like), a laptop computer, a tablet computer, a handheldcomputer, a gaming device, a wearable communication device (e.g., asmart wristwatch, a pair of smart eyeglasses, and/or the like), or asimilar type of device. In some implementations, user device 240 may beconfigured to communicate with electronic wallet device 210 to providebusiness information associated with a consumer and/or a time period ofa transaction.

Network 250 includes one or more wired and/or wireless networks. Forexample, network 250 may include a cellular network (e.g., a long-termevolution (LTE) network, a code division multiple access (CDMA) network,a 3G network, a 4G network, a 5G network, another type of nextgeneration network, and/or the like), a public land mobile network(PLMN), a local area network (LAN), a wide area network (WAN), ametropolitan area network (MAN), a telephone network (e.g., the PublicSwitched Telephone Network (PSTN)), a private network, an ad hocnetwork, an intranet, the Internet, a fiber optic-based network, a cloudcomputing network, and/or the like, and/or a combination of these orother types of networks.

Transaction backend 260 includes one or more devices capable ofauthorizing and/or facilitating a transaction. For example, transactionbackend 260 may include one or more servers and/or computers to storeand/or provide information (e.g., authorizations, balances, transactiontokens, security information, account information, and/or the like)associated with processing a transaction via transaction terminal 230.

Transaction backend 260 may include one or more devices associated withfinancial institutions (e.g., banks, credit unions, and/or the like)and/or transaction card associations that authorize the transactionand/or facilitate a transfer of funds or payments between an account ofa cardholder of smart transaction card 220 and an account of anindividual or business of transaction terminal 230. For example,transaction backend 260 may include one or more devices of one or moreissuing financial institutions associated with a cardholder oftransaction cards in electronic wallet device 210, one or more devicesof one or more acquiring financial institutions (or merchant banks)associated with transaction terminal 230, and/or one or more devicesassociated with one or more card associations (e.g., VISA®, MASTERCARD®,and/or the like) associated with transaction cards of electronic walletdevice 210. Accordingly, in response to receiving transaction card dataassociated with transaction cards of electronic wallet device 210 fromtransaction terminal 230, various financial institutions and/or cardassociations of transaction backend 260 may communicate to authorize thetransaction and/or transfer funds between the accounts associated withtransaction cards of electronic wallet device 210 and/or transactionterminal 230.

Transaction backend 260 may include one or more devices associated witha rewards program associated with transaction cards in electronic walletdevice 210 and/or an entity (e.g., a bank, a merchant, a serviceprovider, a vendor, and/or the like) associated with transaction cardsin electronic wallet device 210 and/or an entity associated withtransaction terminal 230. For example, transaction backend 260 mayauthorize earning and/or redeeming of rewards (e.g., rewards pointsassociated with transaction cards in electronic wallet device 210, cashrewards, client loyalty rewards associated with an entity associatedwith transaction terminal 230, and/or the like) based on a transactionprocessed by transaction terminal 230 with smart transaction card 220and/or transaction cards in electronic wallet device 210.

Cloud computing environment 270 includes an environment that deliverscomputing as a service, whereby shared resources, services, etc. may beprovided to electronic wallet device 210, smart transaction card 220,and/or user device 240. Cloud computing environment 270 may providecomputation, software, data access, storage, and/or other services thatdo not require end-user knowledge of a physical location andconfiguration of a system and/or a device that delivers the services. Asshown, cloud computing environment 270 may include computing resource275.

Computing resource 275 includes one or more personal computers,workstation computers, server devices, or another type of computationand/or communication device. In some implementations, computing resource275 may host business platform 280. The cloud resources may includecompute instances executing in computing resource 275, storage devicesprovided in computing resource 275, data transfer devices provided bycomputing resource 275, etc. In some implementations, computing resource275 may communicate with other computing resources 275 via wiredconnections, wireless connections, or a combination of wired andwireless connections.

As further shown in FIG. 2, computing resource 275 may include a groupof cloud resources, such as one or more applications (“APPs”) 275-1, oneor more virtual machines (“VMs”) 275-2, virtualized storage (“VSs”)275-3, one or more hypervisors (“HYPs”) 275-4, or the like.

Application 275-1 includes one or more software applications that may beprovided to or accessed by user device 240. Application 275-1 mayeliminate a need to install and execute the software applications onuser device 240. For example, application 275-1 may include softwareassociated with business platform 280 and/or any other software capableof being provided via cloud computing environment 270. In someimplementations, one application 275-1 may send/receive informationto/from one or more other applications 275-1, via virtual machine 275-2.

Virtual machine 275-2 includes a software implementation of a machine(e.g., a computer) that executes programs like a physical machine.Virtual machine 275-2 may be either a system virtual machine or aprocess virtual machine, depending upon use and degree of correspondenceto any real machine by virtual machine 275-2. A system virtual machinemay provide a complete system platform that supports execution of acomplete operating system (“OS”). A process virtual machine may executea single program, and may support a single process. In someimplementations, virtual machine 275-2 may execute on behalf of a user(e.g., user device 240), and may manage infrastructure of cloudcomputing environment 270, such as data management, synchronization, orlong-duration data transfers.

Virtualized storage 275-3 includes one or more storage systems and/orone or more devices that use virtualization techniques within thestorage systems or devices of computing resource 275. In someimplementations, within the context of a storage system, types ofvirtualizations may include block virtualization and filevirtualization. Block virtualization may refer to abstraction (orseparation) of logical storage from physical storage so that the storagesystem may be accessed without regard to physical storage orheterogeneous structure. The separation may permit administrators of thestorage system flexibility in how the administrators manage storage forend users. File virtualization may eliminate dependencies between dataaccessed at a file level and a location where files are physicallystored. This may enable optimization of storage use, serverconsolidation, and/or performance of non-disruptive file migrations.

Hypervisor 275-4 provides hardware virtualization techniques that allowmultiple operating systems (e.g., “guest operating systems”) to executeconcurrently on a host computer, such as computing resource 275.Hypervisor 275-4 may present a virtual operating platform to the guestoperating systems, and may manage the execution of the guest operatingsystems. Multiple instances of a variety of operating systems may sharevirtualized hardware resources.

Business platform 280 includes one or more devices capable of receiving,generating, storing, processing, and/or providing information associatedwith maintaining business information (e.g., business informationassociated with a consumer associated with electronic wallet device210). Business platform 280 may include a server device or a group ofserver devices. Business platform 280 may be hosted in cloud computingenvironment 270. Notably, while implementations described hereindescribe business platform as being hosted in cloud computingenvironment 270, in some implementations, business platform 280 may notbe cloud-based or may be partially cloud-based. In some implementations,business platform 280 may include or be associated with a businessenterprise portal that may be accessible to employees or contractors ofan organization of business platform 280.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2. Furthermore, two or more devices shown in FIG. 2 may beimplemented within a single device, or a single device shown in FIG. 2may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) ofenvironment 200 may perform one or more functions described as beingperformed by another set of devices of environment 200.

FIG. 3 is a diagram of example components of a device 300. Device 300may correspond to electronic wallet device 210, smart transaction card220, transaction terminal 230, user device 240, transaction backend 260,computing resource 275, and/or business platform 280. In someimplementations, electronic wallet device 210, smart transaction card220, transaction terminal 230, user device 240, and/or transactionbackend 260 may include one or more devices 300 and/or one or morecomponents of device 300. As shown in FIG. 3, device 300 may include abus 310, a processor 320, a memory 330, a storage component 340, aninput component 350, an output component 360, and a communicationinterface 370.

Bus 310 may include a component that permits communication among thecomponents of device 300. Processor 320 is implemented in hardware,firmware, or a combination of hardware and software. Processor 320 is acentral processing unit (CPU), a graphics processing unit (GPU), anaccelerated processing unit (APU), a microprocessor, a microcontroller,a digital signal processor (DSP), a field-programmable gate array(FPGA), an application-specific integrated circuit (ASIC), or anothertype of processing component. In some implementations, processor 320includes one or more processors capable of being programmed to perform afunction. Memory 330 includes a random access memory (RAM), a read onlymemory (ROM), and/or another type of dynamic or static storage device(e.g., a flash memory, a magnetic memory, and/or an optical memory) thatstores information and/or instructions for use by processor 320.

Storage component 340 stores information and/or software related to theoperation and use of device 300. For example, storage component 340 mayinclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, and/or a solid state memory), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 350 includes a component that permits device 300 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 350 mayinclude a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, and/or anactuator). Output component 360 includes a component that providesoutput information from device 300 (e.g., a display, a speaker, and/orone or more light-emitting diodes (LEDs)).

Communication interface 370 includes a transceiver-like component (e.g.,a transceiver and/or a separate receiver and transmitter) that enablesdevice 300 to communicate with other devices, such as via a wiredconnection, a wireless connection, or a combination of wired andwireless connections. Communication interface 370 may permit device 300to receive information from another device and/or provide information toanother device. For example, communication interface 370 may include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a RF interface, a universal serial bus (USB)interface, a Wi-Fi interface, a cellular network interface, a Bluetoothinterface, a BLE interface, and/or the like.

Device 300 may perform one or more processes described herein. Device300 may perform these processes based on processor 320 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 330 and/or storage component 340. Acomputer-readable medium is defined herein as a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions may be read into memory 330 and/or storagecomponent 340 from another computer-readable medium or from anotherdevice via communication interface 370. When executed, softwareinstructions stored in memory 330 and/or storage component 340 may causeprocessor 320 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 3 are provided asan example. In practice, device 300 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3. Additionally, or alternatively, aset of components (e.g., one or more components) of device 300 mayperform one or more functions described as being performed by anotherset of components of device 300.

FIG. 4 is a flow chart of an example process 400 that may be implementedin association with an electronic wallet device described herein. Insome implementations, one or more process blocks of FIG. 4 may beperformed by electronic wallet device 210. In some implementations, oneor more process blocks of FIG. 4 may be performed by another device or agroup of devices separate from or including electronic wallet device210, such as smart transaction card 220, transaction terminal 230, userdevice 240, and/or transaction backend 260.

As shown in FIG. 4, process 400 may include receiving transactioninformation associated with a transaction at a transaction terminal(block 410). For example, electronic wallet device 210 may receive thetransaction information from transaction terminal 230. In someimplementations, electronic wallet device 210 may receive thetransaction information from smart transaction card 220 and/or userdevice 240 based on a transaction being initiated at transactionterminal 230.

According to some implementations, electronic wallet device 210, smarttransaction card 220, and/or user device 240 may obtain transactioninformation from transaction terminal 230 via an interaction withtransaction terminal 230. For example, electronic wallet device 210,smart transaction card 220, and/or user device 240 may receivetransaction information from transaction terminal 230 when placed incommunication with transaction terminal 230. Accordingly, electronicwallet device 210 may receive the transaction information directly fromtransaction terminal 230 (e.g., via a communication interface ofelectronic wallet device 210) and/or may receive transaction informationindirectly from transaction terminal 230 via smart transaction card 220and/or user device 240.

In some implementations, electronic wallet device 210 may receive thetransaction information via a communication interface of the electronicwallet device 210. For example, the communication interface may enableelectronic wallet device 210 to communicate with transaction terminal230, with smart transaction card 220, and/or with user device 240. Insome implementations, the communication interface of electronic walletdevice 210 may include wired and/or wireless communication interfaces.For example, electronic wallet device 210 may include a terminalinterface that includes an IC chip, magnetic strip, RF antenna and/orthe like that enables electronic wallet device 210 to communicate withan interface (e.g., a magnetic strip reader, a chip reader, an NFCsession terminal, and/or the like) of transaction terminal 230. In someimplementations, electronic wallet device 210 may include a wirelesscommunication interface (e.g., a Bluetooth communication interface, aBLE interface, a Wi-Fi interface, an NFC interface, and/or the like) toreceive or obtain the transaction information from transaction terminal230, smart transaction card 220, and/or user device 240.

According to some implementations, the transaction informationassociated with the transaction may include information associated withan entity that owns and/or operates transaction terminal 230. Forexample, the transaction information may include a merchant identifier(e.g., information indicating a merchant category associated withtransaction terminal 230), acceptable forms of payment for thetransaction (e.g., credit payments, debit payments, and/or the like),acceptable types of transaction cards that may be used in thetransaction (e.g., acceptable card associations that may be used (e.g.,VISA®, MASTERCARD®, AMERICAN EXPRESS®, DISCOVER®, and/or the like)), amonetary value associated with the transaction, a currency used in thetransaction, location information corresponding to a location of thetransaction, and/or the like.

In this way, electronic wallet device 210 may receive transactioninformation associated with a transaction at a transaction terminal thatmay be used to select a transaction card to be used in the transaction.

As further shown in FIG. 4, process 400 may include identifying businessinformation associated with the transaction at the transaction terminal(block 420). For example, electronic wallet device 210 may identifyand/or obtain the business information. In some implementations,electronic wallet device 210 may identify the business information basedon receiving transaction information from transaction terminal 230.

According to some implementations, business information may beassociated with a transaction based on time, location, and/ortransaction information that may be coincidental to the businessinformation and the transaction. For example, electronic wallet device210 may determine, based on the business information, that a transactionis a business transaction if the transaction takes place during aparticular time period, at or near a particular location, with aparticular merchant, with a particular type of merchant, if less (ormore) than a particular amount of currency, and/or the like.

In some implementations, electronic wallet device 210 may receive thebusiness information from user device 240, business platform 280, and/ora user input. For example, user device 240 may provide the businessinformation (e.g., in response to a request for the business informationfrom electronic wallet device 210) via a user device interface ofelectronic wallet device 210 (e.g., a communication interface of a hubof electronic wallet device 210). Additionally, or alternatively,electronic wallet device 210 may obtain the business information frombusiness platform 280. For example, electronic wallet device 210 mayaccess a business account (e.g., a user profile) associated with aconsumer of electronic wallet device 210 and maintained by businessplatform 280. Furthermore, electronic wallet device 210 may include auser interface that enables a consumer of the electronic wallet deviceto input or provide business information (e.g., an input that indicatesthat the transaction is associated with a business transaction).

In some implementations, the business information may include a calendarevent indicating that the transaction is associated with a businesstransaction. For example, electronic wallet device 210 may identifyand/or obtain a calendar event, such as an itinerary, a reservation, anappointment, a meeting, and/or the like that indicates that thetransaction may be business related (i.e., may be a businesstransaction). For example, if the transaction takes place during a timeperiod that corresponds to the calendar event, electronic wallet device210 may determine that the transaction is business transaction.Furthermore, the business information may include an entire electroniccalendar. For example, the electronic calendar may be a businesscalendar of a consumer of the electronic wallet device 210 that includesday-to-day business-related events, meetings, travel, dining, and/or thelike. As such, if a transaction takes place during or within a thresholdtime period of one of the calendar events of the business calendar,electronic wallet device 210 may determine that the transaction is abusiness transaction.

In some implementations, the business information may include a messageindicating that the transaction is associated with a businesstransaction. For example, electronic wallet device 210 may identify anemail, a text message, a voicemail transcription, and/or the like thatindicates that the transaction may be business related. Morespecifically, the message may reference the transaction, may reference amerchant identifier associated with the transaction terminal, mayreference an organization or location of the transaction, may referencea business meeting to take place during the transaction, and/or thelike. As such, electronic wallet device 210 may determine, based on themessage, that the transaction is business related. In someimplementations, electronic wallet device 210 (and/or user device 240)may utilize artificial intelligence (AI) and/or machine learning toanalyze messages associated with a business. Accordingly, electronicwallet device 210 (and/or user device 240) may determine, over time,which messages may indicate business related transactions and whichmessages do not indicate business related transactions.

In some implementations, the business information may include authorizedbusiness transaction information. For example, electronic wallet device210 may identify one or more lists of authorized merchants, authorizedtypes of merchants (e.g., which may be identified via the merchantidentifier), authorized locations of transactions, approved spendinglimits (e.g., for certain merchants, merchant types, for certain timeperiods (e.g., a day, a week, a year, and/or the like). In someimplementations, electronic wallet device 210 may determine that atransaction is a business transaction based on a merchant identifier ofthe transaction information. Accordingly, electronic wallet device 210may compare the authorized business transaction information withcharacteristics of the transaction information (e.g., from transactionterminal 230) to determine whether the transaction is an authorizedtransaction.

In some implementations, the business information may include locationinformation indicating that the transaction is associated with abusiness transaction. The location information may be identified fromthe transaction information, messaging information, calendarinformation, and/or the like. For example, electronic wallet device 210may identify one or more locations or regions associated with a businesstransaction (e.g., within a threshold distance of an office of abusiness organization, within a region or country of a businessorganization, and/or the like). As such, if electronic wallet device 210determines that a transaction takes place within a threshold distance ofa location designated for business transactions, electronic walletdevice 210 may determine that the transaction is a business transaction.

In some implementations, electronic wallet device 210 may obtainbusiness information from one or more applications hosted by user device240 and/or business platform 280. For example, user device 240 mayobtain the business information via a calendar application, a messagingapplication, a location tracking system, or business platform 280.

In this way, electronic wallet device 210, smart transaction card 220,and/or user device 240 may identify business information associated withthe transaction.

As further shown in FIG. 4, process 400 may include selecting atransaction card from a plurality of transaction cards in an electronicwallet device based on the transaction information and the businessinformation (block 430). For example, electronic wallet device 210 mayselect the transaction card from transaction cards that are insertedinto card slots of electronic wallet device 210. In someimplementations, electronic wallet device 210 may select the transactioncard based on receiving transaction information (and/or a notificationof a pending transaction) from transaction terminal 230.

In some implementations, electronic wallet device 210 may identify theplurality or set of transaction cards based on which card slots of theelectronic wallet device 210 include transaction cards. For example,electronic wallet device 210 may determine which card slots ofelectronic wallet device 210 include transaction cards. Electronicwallet device 210 may determine which card slots are holding transactioncards based on determining whether corresponding card readers in thecard slots are communicatively coupled (e.g., in physical contact) withIC chips of transaction cards in the card slots. Accordingly, electronicwallet device 210 may hold transaction cards that are available to beused in a transaction at transaction terminal 230. Further electronicwallet device 210 may identify the transaction cards held by electronicwallet device 210 as a set of candidate transaction cards that may beused in a transaction. When selecting a transaction card from a set oftransaction cards or a plurality of transaction cards, electronic walletdevice may select at least one of the transaction cards from at leasttwo transaction cards.

In some implementations, electronic wallet device 210 may obtain cardinformation associated with the transaction cards in electronic walletdevice 210. For example, electronic wallet device 210 may obtain thecard information from transaction backend 260 (e.g., via user device240), from a data structure of electronic wallet device 210, via userinput, and/or the like. Card information may include an accountidentifier (e.g., a name, an account number, and/or the like associatedwith the account), a card type, a card association, a credit limit, abalance of the account, a type of the account, and/or the like. In someimplementations, electronic wallet device 210 may access, via cardreaders, business account information associated with the transactioncards (e.g., business account numbers, business organization names,business account tier, and/or the like) from IC chips of the transactioncards. In such instances, electronic wallet device 210 may use thebusiness account information to determine that the transaction card isdesignated for use in business transactions. Accordingly, whenelectronic wallet 210 determines, based on the transaction informationand the business information, that the transaction is a businesstransaction, electronic wallet device may select the transaction cardthat is designed for use in business transactions. Alternatively, ifelectronic wallet device determines from the business information (orlack of business information), that a transaction is not a businesstransaction, then electronic wallet device 210 may select a non-businesstransaction card (e.g., a personal transaction card).

According to some implementations, electronic wallet device 210 selectsa transaction card from the transaction cards in electronic walletdevice 210 by analyzing business information associated with atransaction with respect to the transaction information of atransaction. For example, electronic wallet device 210 may develop ahierarchy of transaction rules that indicate when a transaction is abusiness transaction or a non-business transaction based on the businessinformation and transaction information. For example, using a merchantidentifier from the transaction information, electronic wallet device210 may determine which transaction card may be used for a businesstransaction or non-business transaction based on whether the merchantidentifier is associated with a business transaction (as indicated bythe business information).

In some implementations, electronic wallet device 210 may considermultiple non-business related factors when selecting a transaction cardafter determining the transaction card is business transaction or anon-business transaction. For example, electronic wallet device 210 mayconsider rewards earning potential (e.g., which may be based on themerchant identifier), credit limits, account balances, transaction cardtype, and/or the like. Accordingly, if multiple business transactioncards or multiple non-business transaction cards are included inelectronic wallet device 210, electronic wallet device 210 may selectfrom the business transaction cards and the non-business transactioncards based on the non-business related factors.

In some implementations, electronic wallet device 210 may select abusiness transaction card for a business transaction or a non-businesstransaction card for non-business transactions based on one or moresettings of electronic wallet device 210. For example, via a user inputand/or user device 240, a preference may be indicated for certaintransaction cards to be used by default, at particular locations, atparticular times (e.g., of the week, of the month, and/or the like), atparticular merchants or merchant types, and/or the like. Accordingly,settings or rules that electronic wallet device 210 may use to selecttransaction cards may be configurable.

In some implementations, electronic wallet device 210 may utilize ascoring system to select a transaction card from the plurality oftransaction cards based on the transaction information and/or thebusiness information. For example, scores and/or weights may be appliedto the transaction information and/or business information. Scores maybe calculated for each of the transaction cards in electronic walletdevice 210 based on the scoring system, and the transaction card thatsatisfies a threshold value (e.g., is the greatest value or least value)relative to the others may be selected. Accordingly, an optimaltransaction card (i.e., optimal relative to the scoring system) may beselected from the plurality of transaction cards in electronic walletdevice 210 for business transactions and/or non-business transactions attransaction terminal 230. As an example, a first business transactioncard that incurs foreign transaction fees may offer three times bonusrewards points for a business transaction while a second businesstransaction card that does not include foreign transaction fees mayoffer two times bonus rewards points. Depending on weighting of ascoring system used to select the transaction card, electronic walletdevice 210 may select the first business transaction card for thebusiness transaction if rewards information is more weighted thanavoiding transaction fees (or foreign transaction fees) or the secondbusiness transaction card may be selected for the business transactionif avoiding transaction fees is more weighted than rewards information.

Accordingly, electronic wallet device 210 may select a transaction cardfor use in the transaction at transaction terminal 230 based ontransaction information associated with the transaction and/or businessinformation associated with transaction cards in electronic walletdevice 210. In this way, electronic wallet device 210 may facilitateprocessing the transaction by providing a transaction token from theselected transaction card.

As further shown in FIG. 4, process 400 may include providing atransaction token of the selected transaction card to facilitateprocessing the transaction (block 440). For example, electronic walletdevice 210 may provide the transaction token to transaction terminal230. In some implementations, electronic wallet device 210 may providethe transaction token based on selecting the transaction card for thetransaction.

According to some implementations, electronic wallet device 210 mayprovide the transaction token directly to transaction terminal 230and/or indirectly to transaction terminal 230 (e.g., via smarttransaction card 220 and/or user device 240). For example, electronicwallet device 210 may provide the transaction token via a terminalinterface of electronic wallet device 210 and/or via a wirelesscommunication interface of electronic wallet device 210. Accordingly,electronic wallet device 210 may communicate the transaction token totransaction terminal 230, such that transaction terminal 230 may processthe transaction.

In some implementations, electronic wallet device 210 obtains thetransaction token from the transaction card via a card reader ofelectronic wallet device 210 in communication with the transaction card.For example, a card reader of electronic wallet device 210 may obtainthe transaction token from an IC chip of the transaction card andforward the transaction token to the transaction terminal 230. Atransaction token may be any key, code, or security data used tofacilitate processing a transaction. For example, the transaction tokenmay be an encrypted key that authorizes a transfer of funds throughtransaction backend 260 (e.g., from a financial institution of aconsumer associated with electronic wallet device 210 to a financialinstitution associated with an entity of transaction terminal 230).

In this way, electronic wallet device 210 may be used to select atransaction card from a plurality of transaction cards that may be usedto process a transaction at transaction terminal 230 based oninformation associated with transaction terminal 230 and/or theplurality of transaction cards. Accordingly, the transaction card may beused in connection with a transaction terminal to process thetransaction.

Although FIG. 4 shows example blocks of process 400, in someimplementations, process 400 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 4. Additionally, or alternatively, two or more of theblocks of process 400 may be performed in parallel.

FIG. 5 is a flow chart of an example process 500 that may be implementedin association with a smart transaction card and an electronic walletdevice described herein. In some implementations, one or more processblocks of FIG. 5 may be performed by smart transaction card 220. In someimplementations, one or more process blocks of FIG. 5 may be performedby another device or a group of devices separate from or including smarttransaction card 220, such as electronic wallet device 210, transactionterminal 230, user device 240, and/or transaction backend 260.

As shown in FIG. 5, process 500 may include obtaining transactioninformation associated with a transaction at a transaction terminal(block 510). For example, smart transaction card 220 may obtain thetransaction information. In some implementations, smart transaction card220 obtains the transaction information based on detecting aninteraction with transaction terminal 230, such as smart transactioncard 220 detecting that smart transaction card 220 has been insertedinto a chip reader of transaction terminal 230 or smart transaction card220 is within range to hold an NFC session with transaction terminal230.

As described above, the transaction information may include a merchantidentifier, information indicating acceptable forms of payment,information indicating acceptable types of transaction cards, a monetaryvalue of the transaction, a currency of the transaction, a location ofthe transaction, and/or the like. Smart transaction card 220 may obtainthe transaction information by transaction terminal 230 indicating orproviding the transaction information to smart transaction card 220based on the interaction with smart transaction card 220.

In this way, smart transaction card 220 may obtain transactioninformation associated with a transaction from transaction terminal 230.

As further shown in FIG. 5, process 500 may include providing thetransaction information to an electronic wallet device (block 520). Forexample, smart transaction card 220 may provide the transactioninformation to the electronic wallet device 210. In someimplementations, smart transaction card 220 may provide the transactioninformation to electronic wallet device 210 based on obtaining thetransaction information.

According to some implementations, smart transaction card 220 mayprovide the transaction information to electronic wallet device 210 viaa communication link. For example, smart transaction card 220 mayprovide the transaction information via a Bluetooth communication link,a BLE communication link, a Wi-Fi communication link, an NFC session,and/or the like. In some implementations, smart transaction card 220 mayprovide the transaction information to electronic wallet device 210 viaa network (e.g., network 250). For example, electronic wallet device 210may be at a first location (e.g., a consumer's home) and smarttransaction card 220 may be at a second location (e.g., a merchant). Insuch an example, smart transaction card 220 may send the transactioninformation through one or more networks to electronic wallet device 210(which may then respond through the network with a card selectionnotification and/or transaction token).

In some implementations, smart transaction card 220 may requestelectronic wallet device 210 to provide a transaction token based on theobtained transaction information. For example, smart transaction card220 may send a request message that includes the obtained transactioninformation.

In this way, smart transaction card 220 may provide the transactioninformation to electronic wallet device 210 to enable electronic walletdevice 210 to provide a transaction token for the transaction.

As further shown in FIG. 5, process 500 may include receiving atransaction token associated with a transaction card in the electronicwallet device (530). For example, smart transaction card 220 may receivethe transaction token from electronic wallet device 210. In someimplementations, smart transaction card 220 may receive the transactiontoken from electronic wallet device 210 based on electronic walletdevice 210 receiving the transaction information and/or selecting atransaction card to be used to facilitate processing the transaction.

As described in some implementations herein, the transaction card may beselected by electronic wallet device 210 based on the transactioninformation and/or card information. Accordingly, after selecting thetransaction card, electronic wallet device 210 may obtain thetransaction token from the transaction card and send the transactiontoken to smart transaction card 220.

In this way, smart transaction card 220 may receive a transaction tokenassociated with a transaction card in electronic wallet device 210 toenable smart transaction card 220 to provide the transaction token totransaction terminal 230 to facilitate processing the transaction.

As further shown in FIG. 5, process 500 may include providing thetransaction token to the transaction terminal to facilitate processingthe transaction (block 540). For example, smart transaction card 220 mayprovide the transaction token to transaction terminal 230. In someimplementations, smart transaction card 220 may provide the transactiontoken to the transaction terminal 230 based on receiving the transactiontoken from electronic wallet device 210.

In some implementations, smart transaction card 220 may provide thetransaction token to transaction terminal 230 via a chip reader oftransaction terminal 230. For example, smart transaction card 220 maycommunicate the transaction token via an IC chip of smart transactioncard 220 that is communicatively coupled (e.g., in physical contact)with the chip reader of transaction terminal 230. Accordingly, in someimplementations, smart transaction card 220 may be inserted into a chipreader of transaction terminal 230 to engage in a transaction, retrieveand provide the transaction information, and remain in transactionterminal 230 at least until the transaction is processed by transactionterminal 230 using the received and provided transaction token from thetransaction card of electronic wallet device 210.

In this way, smart transaction card 220 may facilitate processing atransaction at transaction terminal 230 using a transaction token fromone or more transaction cards of electronic wallet device 210.

Although FIG. 5 shows example blocks of process 500, in someimplementations, process 500 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 5. Additionally, or alternatively, two or more of theblocks of process 500 may be performed in parallel.

FIG. 6 is a flow chart of an example process 600 that may be implementedin association with a user device and an electronic wallet devicedescribed herein. In some implementations, one or more process blocks ofFIG. 6 may be performed by user device 240. In some implementations, oneor more process blocks of FIG. 6 may be performed by another device or agroup of devices separate from or including user device 240, such aselectronic wallet device 210, smart transaction card 220, transactionterminal 230, and/or transaction backend 260.

As shown in FIG. 6, process 600 may include receiving a request forbusiness information from an electronic wallet device, where thebusiness information is associated with a transaction (block 610). Forexample, user device 240 may receive the request for the businessinformation from electronic wallet device 210. In some implementations,user device 240 may receive the business information from electronicwallet device 210 based on a transaction being initiated (e.g., viasmart transaction card 220 or user device 240) or pending at transactionterminal 230.

User device 240 may receive the request for business information via acommunication link between user device 240 and electronic wallet device210. The example request may be a message, data packet, and/or the likeproviding information associated with a transaction associated with theelectronic wallet device 210. For example, the request may includeinformation identifying a time period of the transaction. Accordingly,the user device may obtain the business information.

In this way, user device 240 may receive a request for businessinformation for the transaction to cause user device 240 to obtain thebusiness information (e.g., from an application of user device 240and/or business platform 280).

As further shown in FIG. 6, process 600 may include obtaining the cardinformation for the plurality of transaction cards in the electronicwallet device (block 620). For example, user device 240 may obtain thecard information for the plurality of transaction cards. In someimplementations, user device 240 obtains the card information based onreceiving the request from electronic wallet device 210.

As described herein, the business information may include calendarinformation, message information, authorization information, locationinformation, and/or the like. Accordingly, user device 240 may obtainthe business information via a calendar application, a messagingapplication, a location tracking system, business platform 280, and/orthe like. For example, user device 240 may identify calendar events of acalendar application that indicate that the transaction is businessrelated (e.g., based on the transaction being within a time period ofthe calendar event or within a threshold time period of the calendarevent). As another example, user device 240 may scan or analyze messages(e.g., text messages, emails, voicemail transcripts, and/or the like)that were sent or received via a messaging application within athreshold time period of the transaction to determine the messagesinclude business related information associated with the transaction.

In some implementations, user device 240 may obtain business informationfrom business platform 280. For example, user device 240 may requestbusiness information from a business enterprise portal of businessplatform 280 that provides information on business transactionauthorizations of employees of the business enterprise. Morespecifically, the business enterprise portal may indicate that aparticular employee, having a business transaction card in electronicwallet device 210, is authorized to use the business transaction card atparticular times, at particular locations, for particular amounts, forparticular types of purchases, up to a particular limit (e.g. per day,per month, per year), and/or the like.

In some implementations, user device 240 may store the businessinformation. For example, user device 240 may store the businessinformation in a data structure of user device 240. In such cases, thebusiness information may be downloaded and/or installed on user device240 (e.g., from a website, from business platform 280, via user input,via an application, and/or the like).

In this way, user device 240 may obtain business information for thetransaction to permit user device 240 to provide the businessinformation to electronic wallet device 210.

As further shown in FIG. 6, process 600 may include providing thebusiness information to the electronic wallet device, such that theelectronic wallet device may provide, based on the business information,a transaction token from a transaction card of the plurality oftransaction cards for a transaction (block 630). For example, userdevice 240 may provide the business information to electronic walletdevice 210 to enable electronic wallet device 210 to determine whether atransaction is a business transaction or a non-business transaction. Insome implementations, user device 240 may provide the businessinformation to electronic wallet device 210 based on obtaining thebusiness information and/or receiving the request for the businessinformation from electronic wallet device 210. According to someimplementations, user device 240 may provide the business information toelectronic wallet device 210 via a communication link (e.g., a Bluetoothcommunication link, a BLE link, an NFC session link, a Wi-Ficommunication link, and/or the like).

User device 240 may provide the business information to electronicwallet device 210 to enable electronic wallet device 210 to select atransaction card (e.g., either a business transaction card or anon-business transaction card), for a transaction, from the plurality oftransaction cards in electronic wallet device 210 according to someimplementations described herein.

Additionally, or alternatively, user device 240 may select thetransaction card based on the business information and/or transactioninformation received from transaction terminal 230. For example, basedon user device 240 interacting with transaction terminal 230 (e.g., viaan NFC session) to engage in a transaction, user device 240 may select abusiness transaction card or non-business transaction card and providethe card information (e.g., card identification information) with arequest that electronic wallet device 210 provide a transaction token,associated with the selected business transaction card or non-businesstransaction card indicated in the card information, to user device 240.Accordingly, user device 240 may process the transaction using thetransaction token received from electronic wallet device 210.

In this way, user device 240 may be used in association with electronicwallet device 210 to facilitate processing a transaction at transactionterminal 230 according to some implementations described herein.

Although FIG. 6 shows example blocks of process 600, in someimplementations, process 600 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 6. Additionally, or alternatively, two or more of theblocks of process 600 may be performed in parallel.

FIGS. 7A-7C are diagrams of an example implementation 700 relating toexample processes 400, 500, and/or 600 shown in FIGS. 4, 5, and/or 6,respectively. FIGS. 7A-7C show an example of using an electronic walletdevice and a user device to facilitate processing a transaction with asmart transaction card according to some implementations herein.

As shown in FIG. 7A, and by reference number 705, transaction cards 1-3are inserted into an electronic wallet device. The electronic walletdevice may share card information of transaction cards 1-3 with a userdevice, as shown by reference number 710. For example, electronic walletdevice may share an account identifier (e.g., an account number), cardexpiration information, a card verification number, and/or the like withthe user device. As shown by reference number 715, the user deviceidentifies a business transaction card. For example, the user device maydetermine that one of the transaction cards 1-3 is a businesstransaction card based on the card information provided. The cardinformation may include information identifying a business account orthat the card is a business type transaction card.

As shown in FIG. 7B, and by reference number 720, a smart transactioncard associated with the electronic wallet device initiates atransaction at a transaction terminal. The smart transaction card maynotify the electronic wallet device of a pending transaction (or aninitiated transaction) and provides transaction information to theelectronic wallet device, as shown by reference number 725. Further, inFIG. 7B, as shown by reference number 730, the electronic wallet devicerequests the user device to obtain business information (e.g., businessinformation associated with the transaction). In some implementations,the electronic wallet device may obtain the business informationdirectly from an application or data structure (e.g., business platform280) that includes business information of User A.

As further shown in FIG. 7B, and by reference number 735, the userdevice obtains the business information from one or more applications ordata structures that includes business information associated with atime period of the transaction (e.g., within the hour, the day, theweek, and/or the like). As shown, the business information may beassociated with User A's calendar, business email, and/or businessportal. Accordingly, the user device can obtain business informationthat may be associated with transaction.

As shown in FIG. 7C, and by reference number 740, the electronic walletdevice receives the business information from the user device. Forexample, the user device may forward and/or send the businessinformation to the electronic wallet device. The electronic walletdevice may select the transaction card for the transaction based on thebusiness information and the transaction information, as shown byreference number 745. In FIG. 7C, as shown by reference number 750, theelectronic wallet device provides a transaction token from the selectedtransaction card to the smart transaction card. The smart transactioncard then provides the transaction token of the selected card to thetransaction terminal, as shown by reference number 755.

Accordingly, a user device may be used in accordance with an electronicwallet device to obtain business information. In such cases, theelectronic wallet device may use the business information (along withtransaction information) to select a transaction card for a transactionaccording to some implementations described herein.

As indicated above, FIGS. 7A-7C are provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIGS. 7A-7C.

FIGS. 8A-8C are diagrams of an example implementation 800 relating toexample processes 400, 500, and/or 600 shown in FIGS. 4, 5, and/or 6,respectively. FIGS. 8A-8C show an example of using an electronic walletdevice and a user device to facilitate processing a transactionaccording to some implementations herein.

As shown in FIG. 8A, and by reference number 810, transaction cards 1-3are inserted into an electronic wallet device. The card information oftransaction cards 1-3 is shared with the user device, as shown byreference number 820. As shown by reference number 830, the user deviceidentifies a business transaction card.

As shown in FIG. 8B, and by reference number 840, the user deviceassociated with the electronic wallet device initiates a transactionwith a transaction terminal and obtains transaction information. Forexample, the user device may interact with the transaction terminal viaan NFC session to engage in the transaction. As shown by referencenumber 850 in FIG. 8B, the user device obtains business informationassociated with the transaction. As shown by reference number 860, theuser device selects a transaction card from the transaction cards 1-3 inthe electronic wallet based on the business information and transactioninformation.

As shown in FIG. 8C, and by reference number 870, the user deviceobtains a transaction token of the selected transaction card from theelectronic wallet device. For example, the user device may send arequest to electronic wallet device for a transaction token from thetransaction card selected from transaction cards 1-3. In such anexample, the electronic wallet device may obtain the transaction tokenfrom the selected transaction card (e.g., via an IC chip of thetransaction card), and send the transaction token to the user device. Asshown by reference number 880 of FIG. 8C, the user device may providethe transaction token to the transaction terminal to facilitateprocessing the transaction. In some implementations, the user device mayprovide the transaction token to the transaction terminal via an NFCsession (e.g., via a same or separate NFC session that was used toengage in the transaction and obtain the transaction information).

Accordingly, a user device may select a transaction card fromtransaction cards in an electronic wallet device to facilitateprocessing a transaction. The user device may select the transactioncard based on business information associated with the transaction cardand/or transaction information associated with the transaction accordingto some implementations described herein.

As indicated above, FIGS. 8A-8C are provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIGS. 8A-8C.

FIG. 9 is a diagram of an example implementation of an electronic walletdevice 900 described herein. Electronic wallet device 900 may correspondto electronic wallet device 210 of FIG. 2. As shown in FIG. 9,electronic wallet device 900 may include card slots 902 with cardreaders 904 in each of card slots 902. Card readers 904 are configuredto interface with transaction cards (e.g., IC chips of transactioncards) inserted into card slots 902. Although electronic wallet device900 is shown to include four card slots 902, electronic wallet device900 may include more or less than four card slots 902.

The electronic wallet device 900 of FIG. 9 includes a hub 906. As shown,the hub 906 includes a card reader interface 908 that is communicativelycoupled with the card readers 904 of the card slots 902. In someimplementations, hub 906 may include one or more processors (e.g.,processor 320) and/or one or more communication interfaces (e.g.,communication interface 370). For example, the one or more processors ofhub 906 may communicate with other devices (e.g., smart transaction card220, user device 240, business platform 280, and/or the like) and/ornetwork 250 via a Bluetooth communication interface, a BLE interface, aNFC interface, a Wi-Fi communication interface, a cellular communicationinterface, and/or the like. In some implementations, hub 906 may includea user device interface (which may include a wired or wirelesscommunication interface), such that hub 906 may receive businessinformation from user device 240 via the user device interface. In someimplementations, card reader interface 908 may include or be implementedby a switching component that includes one or more switches enabling ordisabling access to card readers 904.

According to some implementations, card slots 902 are configured toreceive transaction cards. As shown in FIG. 9, transaction card 910 isinserted into one of the card slots 902. Transaction card 910 may beinserted such that an IC chip 912 of the transaction card iscommunicatively coupled (e.g., in physical contact) with a correspondingcard reader 904 of the corresponding card slot 902. Accordingly, hub 906may obtain card information associated with transaction card 910 and/ora transaction token from transaction card 910 via card reader 904. Usingthe card reader interface 908, hub 906 may provide the transactionterminal to another device (e.g., smart transaction card 220,transaction terminal 230, user device 240, and/or the like). In someimplementations, hub 906 may be used to receive, request, analyze,and/or compare card information, business information, and/ortransaction information for a transaction according to someimplementations described herein.

In some implementations, electronic wallet device 900 of FIG. 9 mayinclude a user interface (e.g., input component 350, output component360, and/or the like). For example, a user interface of electronicwallet device 900 may enable a user to configure settings for hub 906,enter information associated with transaction cards inserted into thecard slots 902, enter preferences for selecting transaction cards incard slots 902 (e.g., by weighting avoiding transaction fees more thanrewards earning potential or vice versa), and/or the like. In someimplementations, hub 906 may be configured via a user interface ofanother device in communication with electronic wallet device 900 (e.g.,user device 240).

In some implementations, a user interface of electronic wallet device900 may include a mechanical mechanism to select which of thetransaction cards is to be used in a particular transaction and/oravailable for use in a particular transaction. For example, the userinterface may include a mechanical switching apparatus that connectsand/or disconnects the transaction cards in the card slots 902 to/fromthe card reader interface 908. Accordingly, electronic wallet device 900may hold cards in card slots 902 without making them available for usein a transaction.

In some implementations, electronic wallet device 900 may be a wearableitem and/or wearable device and/or included within a wearable itemand/or wearable device. For example, electronic wallet device 900 may beintegrated into an article of clothing (e.g., shorts, pants, a shirt, acoat, under garments, and/or the like), a belt, a bag, a purse, abackpack, a wallet, a wrist band, a sleeve, an arm strap, and/or thelike. Furthermore, in some implementations, card slots 902 with cardreaders 904 may be integrated into the wearable device. For example, thecard slots 902 may be pockets of the wearable device, may be includedwithin pockets of the wearable device, or may appear to be pockets ofthe wearable device. In such cases, the transaction cards may bereceived via openings in the pockets of the wearable device.Accordingly, in some implementations, a consumer may insert transactioncards into a wearable device worn on the consumer's person. As such, thetransaction cards of the electronic wallet device may be worn or held bya consumer in a manner that enables the consumer to carryouttransactions without removing the transaction cards from electronicwallet device 210 of the wearable device. For example, the electronicwallet device may communicate with a transaction terminal via a smarttransaction card (e.g., smart transaction card 220), a user device(e.g., user device 240), and/or any other device that may be moreaccessible to a user than the transaction cards held in the electronicwallet device.

In some implementations, a smart transaction card (e.g., similar tosmart transaction card 220) may be inserted into a card slot 902 ofelectronic wallet device 900. In such cases, the smart transaction cardin the electronic wallet device may serve as a hub and/or communicationdevice to facilitate selection of a transaction card in the remainingcard slots of card slots 902, communication with a transaction terminal(e.g., transaction terminal 230) and/or communication with a user device(e.g., user device 240). Accordingly, a smart transaction card in a cardslot 902 of electronic wallet device 900 may implement the exampleprocesses and devices described herein.

In this way, electronic wallet device 900 may be used to receive and/orhold a plurality of transaction cards and provide a transaction tokenfrom at least one of the plurality of transaction cards according tosome implementations described herein.

As indicated above, FIG. 9 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 9.

FIG. 10 is a diagram of an example implementation of an electronicwallet device 1000 described herein. Electronic wallet device 1000 maycorrespond to electronic wallet device 210 of FIG. 2. In FIG. 10, thereference numbers in common with FIG. 9 identify the same or similarelements. For example, electronic wallet device 1000 may include cardslots 902, card readers 904, hub 906, card reader interface 908, and/orone or more features described above in connection with FIG. 9.

As shown in FIG. 10, electronic wallet device 1000 may be modular inthat electronic wallet device 1000 may add or remove one or more cardslot modules 1002 and/or other components. Accordingly, electronicwallet device 1000 may be adjustable and may hold variable amounts oftransaction cards. As shown in FIG. 10, card slot modules 1002 mayinclude module card readers 1004, module hubs 1006, and/or module cardreader interfaces 1008. In some implementations, when card slot modules1002 are attached (e.g., communicatively coupled) to electronic walletdevice 1000, module hubs 1006 may connect with hub 906 and module cardreader interfaces 1008 may connect with card reader interface 908.Accordingly, when card slot modules 1002 are connected with electronicwallet device 1000, electronic wallet device 1000 may include four cardslots (e.g., similar to electronic wallet device 900 of FIG. 9).

Accordingly, electronic wallet device 1000 may be a modular device thatis capable of adding and/or removing card slots. In someimplementations, other features of electronic wallet devices describedherein may be modular. For example, hub 906 (and/or components of hub906) may be removable and/or replaceable. Accordingly, functionality ofelectronic wallet device 1000 may be adjustable.

As indicated above, FIG. 10 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 10.

FIG. 11 is a diagram of an example implementation of an electronicwallet device 0 described herein. Electronic wallet device 1100 maycorrespond to electronic wallet device 210 of FIG. 2. In FIG. 11, thereference numbers in common with FIG. 9 identify the same or similarelements. For example, electronic wallet device 1100 may include cardslots 902, card readers 904, hub 906, card reader interface 908, and/orone or more features described above in connection with FIG. 9.

As shown in FIG. 11, electronic wallet device 1100 may include aterminal interface 1102 that may directly communicate with a transactionterminal (e.g., transaction terminal 230). For example, terminalinterface 1102 may include a plurality of interfaces to interact with atransaction terminal, such as a magnetic strip, an IC chip, an RFantenna, and/or the like. Accordingly, terminal interface 1102 may beused in a similar manner as a transaction card. As such, terminalinterface 1102 may be used to obtain information (e.g., transactioninformation or notifications of a pending transaction) from atransaction terminal and/or provide information or data (e.g., atransaction token) to a transaction terminal.

As shown in FIG. 11, terminal interface 1102 is connected to card readerinterface 908 of electronic wallet device 1100 via a terminal interfacetether 1104. Terminal interface tether 1104 may include a wiredcommunication interface (e.g., a conductive wire) to connect theterminal interface with hub 906 and/or card reader interface 908.Accordingly, hub 906 may exchange information with transaction terminalsvia terminal interface 1102 through the terminal interface tether 1104.

In the example of FIG. 11, hub 906 of electronic wallet device 1100 mayprovide a transaction token from transaction card 910 and/or transactioncard 1110 to a transaction terminal via terminal interface 1102.

As indicated above, FIG. 11 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 11.

FIG. 12 is a diagram of an example implementation of an electronicwallet device 1200 described herein. Electronic wallet device 1200 maycorrespond to electronic wallet device 210 of FIG. 2. In FIG. 12, thereference numbers in common with FIG. 9 identify the same or similarelements. For example, electronic wallet device 1200 may include cardslots 902, card readers 904, hub 906, card reader interface 908, and/orone or more features described above in connection with FIG. 9.

As shown in FIG. 12, electronic wallet device 1200 may include aterminal interface 1202 that may directly communicate with a transactionterminal (e.g., transaction terminal 230). For example, terminalinterface 1202 may include a plurality of interfaces to interact with atransaction terminal, such as a magnetic strip, an IC chip, an RFantenna, and/or the like. Accordingly, terminal interface 1202 may beused in a similar manner as a terminal interface 1102 of FIG. 11.

As shown in FIG. 12, terminal interface 1202 is located on a terminalinterface slide-out 1204. Terminal interface slide-out 1204 may be amechanism that may be extendable for interaction with a transactionterminal and/or retractable into electronic wallet device 1200. In FIG.12, the terminal interface slide-out may be communicatively coupled withcard reader interface 908 such that hub 906 may obtain transactioninformation from transaction terminals and/or provide information ordata (e.g., transaction tokens) from transaction cards inserted intoelectronic wallet device 1200.

In the example of FIG. 12, hub 906 of electronic wallet device 1200 mayprovide a transaction token from transaction card 910 and/or transactioncard 1210 to a transaction terminal via terminal interface 1202.

As indicated above, FIG. 12 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 12.

Accordingly, examples herein provide an electronic wallet device 210that is capable of selecting a transaction card from a plurality oftransaction cards of electronic wallet device 210 for a particulartransaction. For example, the transaction card may be selected based onbusiness information, transaction information, and/or based on cardinformation (e.g. based on account information and/or based on rewardsinformation) associated with the transaction card. As such, a consumermay utilize electronic wallet device 210 as described herein for anenhanced user experience when entering into transactions (e.g., theconsumer does not have to sift through a plurality of cards, find thecorrect card for a transaction, or choose what is believed to be anoptimal card for the transaction). Moreover, transaction failures may beavoided using electronic wallet device 210 as electronic wallet device210 may not select or use business transaction cards for non-relatedbusiness transactions that may be declined (e.g., by determining that aparticular transaction may cause credit limits of the accounts of thetransaction cards to be reached or exceeded) or non-business transactioncards for business transaction that may be non-refundable, thus savingconsumer resources, monetary resources, and/or transaction terminalresources.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term component is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

Certain user interfaces have been described herein and/or shown in thefigures. A user interface may include a graphical user interface, anon-graphical user interface, a text-based user interface, or the like.A user interface may provide information for display. In someimplementations, a user may interact with the information, such as byproviding input via an input component of a device that provides theuser interface for display. In some implementations, a user interfacemay be configurable by a device and/or a user (e.g., a user may changethe size of the user interface, information provided via the userinterface, a position of information provided via the user interface,and/or the like). Additionally, or alternatively, a user interface maybe pre-configured to a standard configuration, a specific configurationbased on a type of device on which the user interface is displayed,and/or a set of configurations based on capabilities and/orspecifications associated with a device on which the user interface isdisplayed.

It will be apparent that systems and/or methods, described herein, maybe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwarecan be designed to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of possible implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items(e.g., related items, unrelated items, a combination of related andunrelated items, and/or the like), and may be used interchangeably with“one or more.” Where only one item is intended, the term “one” orsimilar language is used. Also, as used herein, the terms “has,” “have,”“having,” or the like are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. An electronic wallet device comprising: aplurality of card slots configured to hold at least two transactioncards, each card slot, of the plurality of card slots, including a cardreader; one or more memories; and one or more processors,communicatively coupled to the one or more memories, to: receivetransaction information associated with a transaction at a transactionterminal; identify business information associated with the transaction,the business information relating to whether the transaction isdetermined to be associated with a business-related expense associatedwith a user, the business information being obtained from a user deviceof the user, the business information including at least one of:calendar information associated with the transaction,  the calendarinformation being associated with a business calendar of the userdevice,  the business calendar indicating a business-related event,  thebusiness-related event being within a threshold time period of thetransaction, message information associated with the transaction,  themessage information being analyzed, using artificial intelligence ormachine learning, to indicate whether the message information isassociated with a business transaction, authorization informationassociated with the transaction,  the authorization information beingassociated with an application indicating allowable businesstransactions, or location information associated with the transaction, the location information relating to a location associated with abusiness transaction,  the location being within a threshold distance ofanother location designated for business transactions; automaticallyselect a transaction card from the at least two transaction cardsreceived in respective slots of the plurality of card slots based on thetransaction information and the business information; and provide atransaction token, associated with the selected transaction card, to beused in connection with the transaction terminal to process thetransaction without removing the selected transaction card from arespective card slot.
 2. The electronic wallet device of claim 1, wherethe calendar information comprises: a calendar event indicating that thetransaction is associated with a business transaction, and where the oneor more processors, when automatically selecting the transaction card,are to: automatically select, based on the calendar event, a businesstransaction card, from the at least two transaction cards, that isdesignated for the business transaction.
 3. The electronic wallet deviceof claim 1, where the message information comprises: a messageindicating that the transaction is associated with a businesstransaction, and where the one or more processors, when automaticallyselecting the transaction card, are to: automatically select, based onthe message, a business transaction card, from the at least twotransaction cards, that is designated for the business transaction. 4.The electronic wallet device of claim 1, where the authorizationinformation comprises: authorized business transaction informationindicating that the transaction is associated with a businesstransaction, and where the one or more processors, when automaticallyselecting the transaction card, are to: automatically select, based onthe authorized business transaction information, a business transactioncard, from the at least two transaction cards, that is designated forthe business transaction.
 5. The electronic wallet device of claim 1,where the one or more processors are further to: determine that thebusiness information indicates that the transaction is not associatedwith a business transaction, where the one or more processors, whenautomatically selecting the transaction card, are to: automaticallyselect the transaction card based on the business information indicatingthat the transaction is not associated with a business transaction. 6.The electronic wallet device of claim 1, where the transactioninformation comprises: a merchant identifier indicating a type ofmerchant that is associated with the transaction terminal, and where theone or more processors, when automatically selecting the transactioncard, are to: automatically select the transaction card based on thebusiness information indicating that the merchant identifier indicatesthat the transaction is associated with a business transaction.
 7. Theelectronic wallet device of claim 1, where the user device is to obtainthe business information via at least one of a calendar application, amessaging application, a location tracking system, or a businessplatform.
 8. The electronic wallet device of claim 1, furthercomprising: a user device interface, and where the one or moreprocessors, when receiving the business information, are to: receive thebusiness information from the user device via the user device interfaceof the electronic wallet device.
 9. The electronic wallet device ofclaim 1, where the one or more processors are further to: obtainbusiness account information associated with the transaction card,where, when automatically selecting the transaction card, the one ormore processors are to: automatically select the transaction card basedon the business account information associated with the transactioncard.
 10. A non-transitory computer-readable medium storinginstructions, the instructions comprising: one or more instructionsthat, when executed by one or more processors of an electronic walletdevice, cause the one or more processors to: receive transactioninformation associated with a transaction at a transaction terminal;identify business information associated with a time period of thetransaction, the business information relating to whether thetransaction is determined to be associated with a business-relatedexpense associated with a user, the business information being obtainedfrom a user device of the user, the business information including atleast one of: calendar information associated with the transaction,  thecalendar information being associated with a business calendar of theuser device,  the business calendar indicating a business-related event, the business-related event being within the time period of thetransaction, message information associated with the transaction,  themessage information being analyzed, using artificial intelligence ormachine learning, to indicate whether the message information isassociated with a business transaction, authorization informationassociated with the transaction,  the authorization information beingassociated with an application indicating allowable businesstransactions, or location information associated with the transaction, the location information relating to a location associated with abusiness transaction,  the location being within a threshold distance ofanother location designated for business transactions; identify a set ofcandidate transaction cards to be used for the transaction, the set ofcandidate transaction cards comprising respective integrated circuit(IC) chips that are communicatively coupled with a card reader of theelectronic wallet device; automatically select a transaction card fromthe set of candidate transaction cards that are communicatively coupledwith the card reader of the electronic wallet device, the transactioncard being selected based on the business information; and provide atransaction token, associated with the transaction card, to thetransaction terminal without communicatively uncoupling the selectedtransaction card from the card reader of the electronic wallet device.11. The non-transitory computer-readable medium of claim 10, where theone or more instructions, when executed by the one or more processors,further cause the one or more processors to: identify a businesstransaction card in the set of candidate transaction cards, the businesstransaction card for use in business transactions; and determine, basedon the business information and the transaction information, that thetransaction is one of the business transactions, where the one or moreinstructions, that cause the one or more processors to automaticallyselect the transaction card, cause the one or more processors to:automatically select the business transaction card based on determiningthat the transaction is the one of the business transactions.
 12. Thenon-transitory computer-readable medium of claim 10, where the userdevice is in communication with the electronic wallet device.
 13. Thenon-transitory computer-readable medium of claim 10, where the one ormore instructions, that cause the one or more processors to identify thebusiness information, cause the one or more processors to: determinethat the transaction is not associated with a business transaction,where the one or more instructions, that cause the one or moreprocessors to automatically select the transaction card, cause the oneor more processors to: automatically select the transaction card basedon the transaction not being associated with the business transaction.14. The non-transitory computer-readable medium of claim 10, where thetransaction information comprises: a merchant identifier indicating atype of merchant that is associated with the transaction terminal, andwhere the one or more instructions, that cause the one or moreprocessors to automatically select the transaction card, cause the oneor more processors to: automatically select the transaction card basedon the transaction information indicating that the merchant identifierindicates that the transaction is associated with a businesstransaction.
 15. A method, comprising: detecting, by an electronicwallet device, a transaction pending at a transaction terminal, theelectronic wallet device holding at least two transaction cards, thetransaction being associated with transaction information; obtaining, bythe electronic wallet device, business information associated with atime period of the transaction, the business information relating towhether the transaction is determined to be associated with abusiness-related expense associated with a user, the businessinformation being obtained from a user device of the user, the businessinformation including at least one of: calendar information associatedwith the transaction, the calendar information being associated with abusiness calendar of the user device,  the business calendar indicatinga business-related event,  the business-related event being within thetime period of the transaction, message information associated with thetransaction, the message information being analyzed, using artificialintelligence or machine learning, to indicate whether the messageinformation is associated with a business transaction, authorizationinformation associated with the transaction, the authorizationinformation being associated with an application indicating allowablebusiness transactions, or location information associated with thetransaction, the location information relating to a location associatedwith a business transaction,  the location being within a thresholddistance of another location designated for business transactions;automatically selecting, by the electronic wallet device, a transactioncard from the at least two transaction cards received in respective cardslots of a plurality of card slots of the electronic wallet device, thetransaction card being selected based on at least one of: the businessinformation, or transaction information associated with the transaction;obtaining, by the electronic wallet device, a transaction tokenassociated with the transaction card; and providing, by the electronicwallet device, the transaction token to the transaction terminal withoutremoving the selected transaction card from a respective card slot ofthe plurality of card slots.
 16. The method of claim 15, furthercomprising: identifying the business information based on the timeperiod, the business information being included within at least one of:a calendar event, included in the calendar information, during the timeperiod, or a message, included in the message information, indicating atime within the time period.
 17. The method of claim 15, furthercomprising: sending a request for the business information, to the userdevice, based on detecting the transaction pending at the transactionterminal, where the business information is to be received from the userdevice.
 18. The method of claim 15, where obtaining the businessinformation comprises: obtaining the business information from at leastone of: the user device; a user input of the electronic wallet device;or a cloud computing environment.
 19. The electronic wallet device ofclaim 1, where the one or more processors, when automatically selectingthe transaction card from the at least two transaction cards comprises:calculating at least two scores for the at least two transaction cards,respectively; and automatically selecting the transaction card based ona score, of the at least two scores calculated for the transaction card,satisfying a threshold value.
 20. The non-transitory computer-readablemedium of claim 10, where the one or more instructions, that cause theone or more processors to automatically select a transaction card fromthe set of candidate transaction cards, cause the one or more processorsto: apply a set of weights for the transaction information and thebusiness information, respectively; and automatically select thetransaction card based on a weight, of the set of weights applied forthe transaction card.